Support for moving Redis read commands to replica connections #360
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously all queries execute on the Redis primary servers, since that gives us transactional safety and guaranteed data synchronisation.
In a heavily-loaded cluster, moving read queries out to the replicas can be an acceptable performance tradeoff. Any query which doesn't modify data will be directed to replicas (if any exist - the primary is used otherwise). Writes still go to the primary.
https://redis.io/docs/latest/commands/readonly/
This is disabled by default - you can opt in for the entire process by setting the
transport_use_read_replica
configuration value, e.g.export MYRIAD_TRANSPORT_USE_READ_REPLICA=1
.